Skip to content

Update change-log.md#463

Closed
particthistle wants to merge 1 commit intojoomla:mainfrom
particthistle:patch-1
Closed

Update change-log.md#463
particthistle wants to merge 1 commit intojoomla:mainfrom
particthistle:patch-1

Conversation

@particthistle
Copy link
Member

@particthistle particthistle commented May 9, 2025

User description

Removed reference to Changelog feature not working.

It was referring to https://issues.joomla.org/tracker/joomla-cms/43505 which was resolved by this PR: joomla/joomla-cms#44652 on Jan 13 2025.


PR Type

Documentation


Description

  • Removed outdated note about Changelog feature not working

  • Updated documentation to reflect resolved Joomla issue


Changes walkthrough 📝

Relevant files
Documentation
change-log.md
Remove obsolete warning about Changelog feature                   

versioned_docs/version-4.4/building-extensions/install-update/installation/change-log.md

  • Deleted note referencing a resolved Joomla issue
  • Clarified that the Changelog feature now works as intended
  • +0/-4     

    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • Removed reference to Changelog feature not working.
    
    It was referring to https://issues.joomla.org/tracker/joomla-cms/43505 which was resolved by this PR: joomla/joomla-cms#44652 on Jan 13 2025.
    @qodo-code-review
    Copy link
    Contributor

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No major issues detected

    @qodo-code-review
    Copy link
    Contributor

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    @HLeithner
    Copy link
    Member

    You removed the warning from 4.4 which actually is not the version where it has been fixed.

    It has been fixed in 5.2, could you please remove the entry from 5.2 and 5.3 and next (/docs) please

    @robbiejackson
    Copy link
    Contributor

    As mentioned, the documentation change was applied to the wrong version. It was easier for me to raise a new PR than amend this one, so I'll close this in favour of #556

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    3 participants